home *** CD-ROM | disk | FTP | other *** search
- Path: dispatch.news.demon.net!demon!gj-cent.demon.co.uk
- From: gi@gj-cent.demon.co.uk (Gi)
- Newsgroups: comp.sys.amiga.misc,comp.sys.amiga.programmer
- Subject: Re: toy operating systems, like AmigaOS
- Date: Sun, 14 Apr 1996 22:37:55 GMT
- Message-ID: <900.6678T300T953@gj-cent.demon.co.uk>
- References: <4krdlk$jge@vixen.cso.uiuc.edu>
- NNTP-Posting-Host: gj-cent.demon.co.uk
- X-NNTP-Posting-Host: gj-cent.demon.co.uk
- X-Newsreader: THOR 2.22 (Amiga;TCP/IP)
-
- howard daniel joseph wrote in <4krdlk$jge@vixen.cso.uiuc.edu> on 14-Apr-96
-
- > Well, there are two ways to go about this;
-
- > 1) Don't write shitty code.
-
- > 2) Write shitty code on a platform that supports shitty code.
-
- > 3) If you want to take the shit out of your code without crashing
- >a system without memory protection, whack your shit around in a more
- >robust environment and then send your shitless code to the Amiga. :)
-
- why be proud of writing bad code? eventually if you write bad code rather than
- crash your system you might corrupt your hard disk or loose you work altogether
- (which hasn't happened here).
-
- The only computers that need to be that safe anyway are those that are keeping
- people safe or those in Aircraft/Spacecraft.
-
- I run a system monitor that checks for bad coding when I use a new program and
- if it fails the test I don't run it, it's that simple.
-
-